👷 do not rely on hardcoded list of DCs #3973
Draft
+268
−104
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We want to avoid hardcoding the list of datacenter in the release process. This will remove the need for creating a PR for new DCs.
For this we need two things:
ddtool.monitorIdsByDatacenter: For this we're querying the logs API directly. Newly created DC might not have api or application key setup so we're skipping the monitors for thoses.Another benefit from this new strategy for monitoring DC deployments is that we're able to only account for the errors related to the version of the SDK currently being deployed. This makes the release more resilient to unrelated monitor alerts.
Changes
datacentervsuploadPathand try to make things more clearsiteByDatacenterin favor of a ddtool commandmonitorIdsByDatacenterin favor of a logs API queryTodos
Test instructions
Checklist